Upgrade compliance BinSkim scanner to 4.4.9 - #8579
Merged
Merged
Conversation
Pin the standalone compliance pipeline to BinSkim scanner version 4.4.9 using the task's Exact version inputs. This avoids the deprecated 1.9.5 default without changing the BinSkim task version.
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
|
🔒 Automated review in progress — Heejae Chang (@heejaechang) is auto-reviewing this PR. |
Contributor
Author
|
/azp run |
|
Azure Pipelines: 1 pipeline(s) were filtered out due to trigger conditions. |
Heejae Chang (heejaechang)
approved these changes
Jul 20, 2026
Heejae Chang (heejaechang)
left a comment
Heejae Chang (heejaechang)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
4.4.9.BinSkim@4; only the scanner binary version changes.Context
BinSkim scanner version
1.9.5is deprecated on July 30, 2026 because it includes a vulnerablemsdia140.dll. PTVS-Compliance invokes the Guardian BinSkim task directly rather than through 1ES Pipeline Templates, so this pipeline requires an explicit upgrade.The July 20 PTVS-Compliance run
26201.1(build14704086) confirmed that the current unpinned configuration resolvesLatestto the deprecated scanner:The installed
BinSkim@4.289.0task represents a custom scanner version withtoolVersion: Exactand the companionexactToolVersioninput, so this PR uses that supported form to select4.4.9.The primary
azure-pipelines.ymlpipeline is unpinned and uses 1ES Pipeline Templates, so it does not require the same change.Validation
BinSkim@4.289.0task schema supportsExactplusexactToolVersion.4.4.9is present in the Guardian internal feed.The next compliance run should report
Running BinSkim 4.4.9in the BinSkim task log.